Description

Related PRS (if any):

This backend PR is related to the #2878 frontend PR(OneCommunityGlobal/HighestGoodNetworkApp#2878).

Main changes explained:

1. Implement a new meeting schema in the database.
2. Implement APIs to post a new meeting, to get all meetings within a specific time range

Known bugs:

The bell does not ring for the first meeting notification displayed but rings for subsequent ones. This happens because browsers block the autoplay of audio or video until the user interacts with the page (e.g., by clicking or tapping). A possible solution could be to display a preview notification for the upcoming meeting, prompting the user to click a button on the page, which would then allow the bell to ring for future notifications.

How to test:

1. check into current branch
2. do npm install and npm run start:local to run this PR locally
3. Clear site data/cache
4. log as admin/owner user
5. go to dashboard→ Other Links→ Schedule Meetings
6. verify that an admin/owner user can fill in the information in the scheduling form. After clicking the "Submit" button, a message should display the details of the meeting the user has just scheduled.
7. Log in as one of the recipients of the scheduled meeting. If the meeting is scheduled within 3 days from the current date, the recipient should see notifications for the meetings they need to attend after logging in. After clicking the "Cancel" button, the current notification should no longer be displayed. Notifications for other meetings, if available, should then be shown.

Screenshots or videos of changes: